As HAProxy is running chrooted by default, we rely on an additional syslog
socket created by rsyslog inside the chroot for logging. As this socket cannot
trigger syslog activation, we explicitly order HAProxy after rsyslog.service.
Note that we are not using syslog.service here, since the additional socket is
rsyslog-specific.
Forwarded: no
Last-Update: 2017-12-01
Gbp-Pq: Name haproxy.service-start-after-syslog.patch
* Non-maintainer upload by the Security Team.
* BUG/MEDIUM: mux-h2: Refuse interim responses with end-stream flag set
(CVE-2023-0056)
* BUG/CRITICAL: http: properly reject empty http header field names
(CVE-2023-25725)